Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1467d9364f509dfe961677508aa9efab0b8772d11bf44ff679c7b65bc8abf75a

Tx prefix hash: cfe32e38736d2e5b4b0db324ec78d4a5fbad2064bdeaf4f0a41b907329d33c47
Tx public key: c3667501cd9de8cc89ed2eeb4ddaa7761bf5197a58fb5862aa4de10e880e249d
Timestamp: 1638960912 Timestamp [UCT]: 2021-12-08 10:55:12 Age [y:d:h:m:s]: 03:328:03:34:55
Block: 391007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1010983 RingCT/type: yes/0
Extra: 01c3667501cd9de8cc89ed2eeb4ddaa7761bf5197a58fb5862aa4de10e880e249d021100000002379224c2000000000000000000

1 output(s) for total of 31.077022722000 dcy

stealth address amount amount idx
00: e4a6c28779482b57126f21e99a9f16b386ab8c1f339651c2d4e357541cb6012f 31.077022722000 787148 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": 391017, "vin": [ { "gen": { "height": 391007 } } ], "vout": [ { "amount": 31077022722, "target": { "key": "e4a6c28779482b57126f21e99a9f16b386ab8c1f339651c2d4e357541cb6012f" } } ], "extra": [ 1, 195, 102, 117, 1, 205, 157, 232, 204, 137, 237, 46, 235, 77, 218, 167, 118, 27, 245, 25, 122, 88, 251, 88, 98, 170, 77, 225, 14, 136, 14, 36, 157, 2, 17, 0, 0, 0, 2, 55, 146, 36, 194, 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