Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eaf7162f5943698c5c1088c20f4a9f8a1d704d0d8f603e44b9ba0c241434e6e0

Tx prefix hash: aea0d0f73d0168ec9f2564c058b0779e80b7c3906a34721a437b9bba7f87fa1b
Tx public key: 70d87f628076392710d4505171c162ef46d2914dcc50d6e04f685d451a5bccb5
Timestamp: 1582975869 Timestamp [UCT]: 2020-02-29 11:31:09 Age [y:d:h:m:s]: 05:090:09:21:07
Block: 74004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1219009 RingCT/type: yes/0
Extra: 0170d87f628076392710d4505171c162ef46d2914dcc50d6e04f685d451a5bccb502110000016412c4732d000000000000000000

1 output(s) for total of 348.985130037000 dcy

stealth address amount amount idx
00: 5aad6ee22f4ee478e8c680807788e7a6753146fb7c2635ae9210fd6e6f2db34a 348.985130037000 136773 of 0

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": 74014, "vin": [ { "gen": { "height": 74004 } } ], "vout": [ { "amount": 348985130037, "target": { "key": "5aad6ee22f4ee478e8c680807788e7a6753146fb7c2635ae9210fd6e6f2db34a" } } ], "extra": [ 1, 112, 216, 127, 98, 128, 118, 57, 39, 16, 212, 80, 81, 113, 193, 98, 239, 70, 210, 145, 77, 204, 80, 214, 224, 79, 104, 93, 69, 26, 91, 204, 181, 2, 17, 0, 0, 1, 100, 18, 196, 115, 45, 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