Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3944f58a4d13b1f11c59b907b8806dbae47f5ebb4d396080d32d71ad45e9715d

Tx prefix hash: 486bbd25a318149dcc773c9c1e0246bbccb783c29ef3d1658ae240f43fc047af
Tx public key: 9753243fbee6f9482cc1c1267161033d84176d5e2e08be956d028055c73698c2
Timestamp: 1737704891 Timestamp [UCT]: 2025-01-24 07:48:11 Age [y:d:h:m:s]: 00:148:16:59:35
Block: 1204143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105961 RingCT/type: yes/0
Extra: 019753243fbee6f9482cc1c1267161033d84176d5e2e08be956d028055c73698c20211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27d8fd45ae801584ef6c72d09677f0a8695cbc6f6f6c68684286fe1e0aa2dd0d 0.600000000000 1690826 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": 1204153, "vin": [ { "gen": { "height": 1204143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27d8fd45ae801584ef6c72d09677f0a8695cbc6f6f6c68684286fe1e0aa2dd0d" } } ], "extra": [ 1, 151, 83, 36, 63, 190, 230, 249, 72, 44, 193, 193, 38, 113, 97, 3, 61, 132, 23, 109, 94, 46, 8, 190, 149, 109, 2, 128, 85, 199, 54, 152, 194, 2, 17, 0, 0, 0, 2, 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