Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2daa3bd301cd206e4fe77659f6207f43615f5af5d38d1f8fe1155798b4305ca

Tx prefix hash: 23bb22fce67b2d74dda22d379fe6665a555dc765791e8ebb47665a78efb27e34
Tx public key: 1cb1e9e6b4b15b498200c661009575cd40e01e8fd830dc2f9b4ab8518656ad0c
Timestamp: 1744332198 Timestamp [UCT]: 2025-04-11 00:43:18 Age [y:d:h:m:s]: 00:027:10:18:52
Block: 1258779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19625 RingCT/type: yes/0
Extra: 011cb1e9e6b4b15b498200c661009575cd40e01e8fd830dc2f9b4ab8518656ad0c0211000000046c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54c547e6e97c4a92308bd676e553816245c6c97b896864b73bbd1bcdc17ca34a 0.600000000000 1745916 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": 1258789, "vin": [ { "gen": { "height": 1258779 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54c547e6e97c4a92308bd676e553816245c6c97b896864b73bbd1bcdc17ca34a" } } ], "extra": [ 1, 28, 177, 233, 230, 180, 177, 91, 73, 130, 0, 198, 97, 0, 149, 117, 205, 64, 224, 30, 143, 216, 48, 220, 47, 155, 74, 184, 81, 134, 86, 173, 12, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 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