Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05138eda9385f1f7dfa5c8ac00744d9eb93d495a5c02bc6b97e9f44c0136745a

Tx prefix hash: 4f9e4b22c30c840ddcf206956f7be415f1bf1b77f07c865e181c270d07447288
Tx public key: 8b8137be403d8671c07e68bb7a90fdbc0b8f1bc27a1b2a1a856bc88c1cea9e5f
Timestamp: 1705548351 Timestamp [UCT]: 2024-01-18 03:25:51 Age [y:d:h:m:s]: 01:143:21:13:59
Block: 937716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363987 RingCT/type: yes/0
Extra: 018b8137be403d8671c07e68bb7a90fdbc0b8f1bc27a1b2a1a856bc88c1cea9e5f0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbe670b32ba8cbc1f3eb22ddefc88bb1b2d3ead14a95b0fc05b0c6bc1295c7ae 0.600000000000 1395778 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": 937726, "vin": [ { "gen": { "height": 937716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbe670b32ba8cbc1f3eb22ddefc88bb1b2d3ead14a95b0fc05b0c6bc1295c7ae" } } ], "extra": [ 1, 139, 129, 55, 190, 64, 61, 134, 113, 192, 126, 104, 187, 122, 144, 253, 188, 11, 143, 27, 194, 122, 27, 42, 26, 133, 107, 200, 140, 28, 234, 158, 95, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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