Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 284664a85386a7d9e3249a305e58eadd80cb3398bd3ca17d09b8850f2efc8a91

Tx prefix hash: f679e219a60cc183ebfb0d13c3c9b585a799f5dd5f61f77c01edb406d87b36b0
Tx public key: f4c4a6e5e7951fe661c153848db08a066d98d9b6d7c449a7996bf25597702158
Timestamp: 1736753364 Timestamp [UCT]: 2025-01-13 07:29:24 Age [y:d:h:m:s]: 00:159:06:18:21
Block: 1196307 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113486 RingCT/type: yes/0
Extra: 01f4c4a6e5e7951fe661c153848db08a066d98d9b6d7c449a7996bf255977021580211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8b50cbc8e1f676d9a0cfefd8934d69261efd16ea1dcac9038206b60dd0fb679 0.600000000000 1682906 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": 1196317, "vin": [ { "gen": { "height": 1196307 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8b50cbc8e1f676d9a0cfefd8934d69261efd16ea1dcac9038206b60dd0fb679" } } ], "extra": [ 1, 244, 196, 166, 229, 231, 149, 31, 230, 97, 193, 83, 132, 141, 176, 138, 6, 109, 152, 217, 182, 215, 196, 73, 167, 153, 107, 242, 85, 151, 112, 33, 88, 2, 17, 0, 0, 0, 4, 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