Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e854c1545c11f6a5821bc1420c676c95a8c3d2190066cfacc88c61e90021fc6a

Tx prefix hash: 46721b240295761cffb7ecb5b0d4ded5a459453c4c4296eb231555925a09133d
Tx public key: 1b074df0c065cbf6cdbf16da8ec0422c346d26699069123816fceff0e9580b0e
Timestamp: 1724811674 Timestamp [UCT]: 2024-08-28 02:21:14 Age [y:d:h:m:s]: 00:248:06:22:51
Block: 1097437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177325 RingCT/type: yes/0
Extra: 011b074df0c065cbf6cdbf16da8ec0422c346d26699069123816fceff0e9580b0e02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4580c6acbd6087d043f6997758a5017d1f482a14d3a90323c2d0c043b6e9db2e 0.600000000000 1572834 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": 1097447, "vin": [ { "gen": { "height": 1097437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4580c6acbd6087d043f6997758a5017d1f482a14d3a90323c2d0c043b6e9db2e" } } ], "extra": [ 1, 27, 7, 77, 240, 192, 101, 203, 246, 205, 191, 22, 218, 142, 192, 66, 44, 52, 109, 38, 105, 144, 105, 18, 56, 22, 252, 239, 240, 233, 88, 11, 14, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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