Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81909acd8de13f465396b1d19d4648ddc5acda2c548646496087f9a74978eee3

Tx prefix hash: 09281b86060fa0cac1af49df8dcd76cff37b94e21a101647c9ce9d14351c78c0
Tx public key: e2f37264e382e88cd72eed40f8c0f06f41b8af4ef3b3c11e1ce4a94d0ff9698c
Timestamp: 1748815433 Timestamp [UCT]: 2025-06-01 22:03:53 Age [y:d:h:m:s]: 00:161:21:40:51
Block: 1295902 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113395 RingCT/type: yes/0
Extra: 01e2f37264e382e88cd72eed40f8c0f06f41b8af4ef3b3c11e1ce4a94d0ff9698c021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aedf44169cdb50eb130e844bcfd60d0cd6744fe39f68dca9237f661e921fc1a6 0.600000000000 1783409 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": 1295912, "vin": [ { "gen": { "height": 1295902 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aedf44169cdb50eb130e844bcfd60d0cd6744fe39f68dca9237f661e921fc1a6" } } ], "extra": [ 1, 226, 243, 114, 100, 227, 130, 232, 140, 215, 46, 237, 64, 248, 192, 240, 111, 65, 184, 175, 78, 243, 179, 193, 30, 28, 228, 169, 77, 15, 249, 105, 140, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 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