Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae7f8d2371be046c694cd091bc3f753adf8d5acf88934759f3e3369ad9f00fb9

Tx prefix hash: 8c78b22fc2d7f02d5f4d3b17ac86d7187323607e067fb9471816b34aba78b571
Tx public key: 59deecbe8b58decd0acc6bb501d5c5481df208fd63ad542d321401b85e04a9f2
Timestamp: 1734838657 Timestamp [UCT]: 2024-12-22 03:37:37 Age [y:d:h:m:s]: 00:171:01:46:37
Block: 1180497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122046 RingCT/type: yes/0
Extra: 0159deecbe8b58decd0acc6bb501d5c5481df208fd63ad542d321401b85e04a9f2021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 139c227f8847782d2d885f2006b94423f93e422e65e502dfa6e18d49428ad09e 0.600000000000 1666908 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": 1180507, "vin": [ { "gen": { "height": 1180497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "139c227f8847782d2d885f2006b94423f93e422e65e502dfa6e18d49428ad09e" } } ], "extra": [ 1, 89, 222, 236, 190, 139, 88, 222, 205, 10, 204, 107, 181, 1, 213, 197, 72, 29, 242, 8, 253, 99, 173, 84, 45, 50, 20, 1, 184, 94, 4, 169, 242, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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