Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2347e38bfcfcbe8d2de2a75c7cf3bed4f29922744f5346cf4d21a886c862ffa

Tx prefix hash: 403a1b76d81f70e8c3e3f6289be34804664feef1b43b6b4dd715ce3b48b5a986
Tx public key: ee35a41aa8953d70e31e9277acbc83e95ba21ee4dcaa16bd4901fa051444ee0d
Timestamp: 1638726040 Timestamp [UCT]: 2021-12-05 17:40:40 Age [y:d:h:m:s]: 03:155:12:56:59
Block: 389102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 889878 RingCT/type: yes/0
Extra: 01ee35a41aa8953d70e31e9277acbc83e95ba21ee4dcaa16bd4901fa051444ee0d02110000000b37cb3088000000000000000000

1 output(s) for total of 31.531998175000 dcy

stealth address amount amount idx
00: 7e55444a82de55c68328b6ae2f5697372ef0a9a4121b1aa87e36d4d24724d730 31.531998175000 784101 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": 389112, "vin": [ { "gen": { "height": 389102 } } ], "vout": [ { "amount": 31531998175, "target": { "key": "7e55444a82de55c68328b6ae2f5697372ef0a9a4121b1aa87e36d4d24724d730" } } ], "extra": [ 1, 238, 53, 164, 26, 168, 149, 61, 112, 227, 30, 146, 119, 172, 188, 131, 233, 91, 162, 30, 228, 220, 170, 22, 189, 73, 1, 250, 5, 20, 68, 238, 13, 2, 17, 0, 0, 0, 11, 55, 203, 48, 136, 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