Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9704986b56e3ec34d87165295dd4f7ee18ee91f1695b6bffd9b3796cd61ed3e5

Tx prefix hash: 523a161ad8d6f3cecc16cc9b0d2f934d5a63db9f4e3845ea66670cb8ea5ad132
Tx public key: 66ce01ba2d8d2069f8a11b18abfe71d6d4d6e3d3a3744183fa97a6d7089ae643
Timestamp: 1736136395 Timestamp [UCT]: 2025-01-06 04:06:35 Age [y:d:h:m:s]: 00:089:22:19:46
Block: 1191208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64042 RingCT/type: yes/0
Extra: 0166ce01ba2d8d2069f8a11b18abfe71d6d4d6e3d3a3744183fa97a6d7089ae64302110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6700c62f5c96b3e29a8fe50969b8c0dd4f4784e3b219ecaa3e2fb13323dc9b65 0.600000000000 1677731 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": 1191218, "vin": [ { "gen": { "height": 1191208 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6700c62f5c96b3e29a8fe50969b8c0dd4f4784e3b219ecaa3e2fb13323dc9b65" } } ], "extra": [ 1, 102, 206, 1, 186, 45, 141, 32, 105, 248, 161, 27, 24, 171, 254, 113, 214, 212, 214, 227, 211, 163, 116, 65, 131, 250, 151, 166, 215, 8, 154, 230, 67, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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