Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 860964a7851b4eaa328ea25d3d6399650e6e335d39f739dda0ef9b6c2e93dd84

Tx prefix hash: 138746e753cbab1c51dc2d8651b11f77dab8c10d02ca61f347c47941418b3c39
Tx public key: bd85980b7172cc83753185f9de7617da249a2b2af935f7274a78aa4c16cae976
Timestamp: 1736308166 Timestamp [UCT]: 2025-01-08 03:49:26 Age [y:d:h:m:s]: 00:295:21:33:38
Block: 1192620 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208986 RingCT/type: yes/0
Extra: 01bd85980b7172cc83753185f9de7617da249a2b2af935f7274a78aa4c16cae9760211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5bbc0a7601cf063eda51dbc772ce1a7a8ce0bc74ea15f8754c5a5deb852a67f 0.600000000000 1679175 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1192630, "vin": [ { "gen": { "height": 1192620 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5bbc0a7601cf063eda51dbc772ce1a7a8ce0bc74ea15f8754c5a5deb852a67f" } } ], "extra": [ 1, 189, 133, 152, 11, 113, 114, 204, 131, 117, 49, 133, 249, 222, 118, 23, 218, 36, 154, 43, 42, 249, 53, 247, 39, 74, 120, 170, 76, 22, 202, 233, 118, 2, 17, 0, 0, 0, 9, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8