Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1121a69845a0ba84f4b35f4bbb9a46ba335b707e34f7170ea5e9631f1ae0845

Tx prefix hash: 6ee6f8a526fc4e1ca74ef69288ca07b09ef3da5baaaa9e1f4b0463d224f000ad
Tx public key: 3d0a92cc9cb33dd008cd4a147bd174a951eff91030468ad3d7af5ed5e2ecf2f5
Timestamp: 1711935393 Timestamp [UCT]: 2024-04-01 01:36:33 Age [y:d:h:m:s]: 01:043:23:45:10
Block: 990712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292409 RingCT/type: yes/0
Extra: 013d0a92cc9cb33dd008cd4a147bd174a951eff91030468ad3d7af5ed5e2ecf2f502110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 601abc09e7f35a3987cae04073802382d4a13d69221c0ed53ea9428464d59141 0.600000000000 1451038 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": 990722, "vin": [ { "gen": { "height": 990712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "601abc09e7f35a3987cae04073802382d4a13d69221c0ed53ea9428464d59141" } } ], "extra": [ 1, 61, 10, 146, 204, 156, 179, 61, 208, 8, 205, 74, 20, 123, 209, 116, 169, 81, 239, 249, 16, 48, 70, 138, 211, 215, 175, 94, 213, 226, 236, 242, 245, 2, 17, 0, 0, 0, 1, 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