Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdaf1f31bb0141a7e47d3913925c34b1143811b0679c8a022c2b0114495239bd

Tx prefix hash: a37b485f1d49da8b2d1b2012657feb30b0a8b7572825c30026210df68dc583fa
Tx public key: a4e525143f2a27bfe6874ef4b20efb0c014cf88b33adbcb754020b914929ea9b
Timestamp: 1713446407 Timestamp [UCT]: 2024-04-18 13:20:07 Age [y:d:h:m:s]: 01:220:05:14:50
Block: 1003208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416086 RingCT/type: yes/0
Extra: 01a4e525143f2a27bfe6874ef4b20efb0c014cf88b33adbcb754020b914929ea9b02110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5101b9e7e42a5324cd0f2040eeab6d51500cdb71a1f1830f3d8d375d218efa20 0.600000000000 1463738 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": 1003218, "vin": [ { "gen": { "height": 1003208 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5101b9e7e42a5324cd0f2040eeab6d51500cdb71a1f1830f3d8d375d218efa20" } } ], "extra": [ 1, 164, 229, 37, 20, 63, 42, 39, 191, 230, 135, 78, 244, 178, 14, 251, 12, 1, 76, 248, 139, 51, 173, 188, 183, 84, 2, 11, 145, 73, 41, 234, 155, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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