Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11be0fcfaebc02fa704df6b28dd7a20a727427bdaa04856861e901d2b8b10d03

Tx prefix hash: a2a958ed71c48374afc54d6727ed7eb3c4f11abdc589e1b62da4ace579e41dab
Tx public key: 4fed1261e262d1445890e6595eb66bd80a95d64637ca7b6e4aa4361a6d95d609
Timestamp: 1751227463 Timestamp [UCT]: 2025-06-29 20:04:23 Age [y:d:h:m:s]: 00:137:12:48:03
Block: 1315381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96459 RingCT/type: yes/0
Extra: 014fed1261e262d1445890e6595eb66bd80a95d64637ca7b6e4aa4361a6d95d609021100000004e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8d4b163c80784a07c28f8a40415d2e90eabfdb4d31c24c1abb5fb6dc4f09b81 0.600000000000 1803036 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": 1315391, "vin": [ { "gen": { "height": 1315381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8d4b163c80784a07c28f8a40415d2e90eabfdb4d31c24c1abb5fb6dc4f09b81" } } ], "extra": [ 1, 79, 237, 18, 97, 226, 98, 209, 68, 88, 144, 230, 89, 94, 182, 107, 216, 10, 149, 214, 70, 55, 202, 123, 110, 74, 164, 54, 26, 109, 149, 214, 9, 2, 17, 0, 0, 0, 4, 228, 220, 144, 9, 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