Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e206bd38eea502cccb82455d9aaf568dd41ac54cca893c78c97d9271fe73f51

Tx prefix hash: 7d47ab2a0020f95d63009385f2b8a931e855de2fea36264c611981d9341f10f4
Tx public key: 8639e877a3890d06b7d4de6e77fb7d4b466b0ca0cb292a11b5f1e7f6b143b41e
Timestamp: 1713608133 Timestamp [UCT]: 2024-04-20 10:15:33 Age [y:d:h:m:s]: 00:251:06:31:13
Block: 1004545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179866 RingCT/type: yes/0
Extra: 018639e877a3890d06b7d4de6e77fb7d4b466b0ca0cb292a11b5f1e7f6b143b41e0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91ec1fadf78a1d72f510ea95a3152c51988aa2ad49fb19a4408b1e58675d78fb 0.600000000000 1465113 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": 1004555, "vin": [ { "gen": { "height": 1004545 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91ec1fadf78a1d72f510ea95a3152c51988aa2ad49fb19a4408b1e58675d78fb" } } ], "extra": [ 1, 134, 57, 232, 119, 163, 137, 13, 6, 183, 212, 222, 110, 119, 251, 125, 75, 70, 107, 12, 160, 203, 41, 42, 17, 181, 241, 231, 246, 177, 67, 180, 30, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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