Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 585cf89fa3f4057de7d13b96ae56eb8c978aed99fa5acb362089bc6c8a4c2dfa

Tx prefix hash: 24c4a3fda64606e437a60e4652ec797636516c5f7595598b7671b1963c4d151f
Tx public key: 5ae1e8010e1431a895b0effed672cb2d9c35f3eeef7198f003c973c9cf0359a4
Timestamp: 1744612067 Timestamp [UCT]: 2025-04-14 06:27:47 Age [y:d:h:m:s]: 00:221:11:58:53
Block: 1261117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156011 RingCT/type: yes/0
Extra: 015ae1e8010e1431a895b0effed672cb2d9c35f3eeef7198f003c973c9cf0359a40211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8f705d062acccb89e61ea8935bae0d58508fce5c22fb7f4aa5f7260dd81ee73 0.600000000000 1748282 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": 1261127, "vin": [ { "gen": { "height": 1261117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8f705d062acccb89e61ea8935bae0d58508fce5c22fb7f4aa5f7260dd81ee73" } } ], "extra": [ 1, 90, 225, 232, 1, 14, 20, 49, 168, 149, 176, 239, 254, 214, 114, 203, 45, 156, 53, 243, 238, 239, 113, 152, 240, 3, 201, 115, 201, 207, 3, 89, 164, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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