Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d89fa0641360e1b773d46c30d9495a44ba278880c47f995a24cc9508ee36c977

Tx prefix hash: c2f7b50ad950c457135d05d46ccafc0f61b578072fac0c65068332d9235c262b
Tx public key: 78ea13fc0cc883da95fba5ac403efcd6339fe8ea2e8383218a526c1eee1b4e31
Timestamp: 1644735037 Timestamp [UCT]: 2022-02-13 06:50:37 Age [y:d:h:m:s]: 02:331:02:08:34
Block: 437554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 755939 RingCT/type: yes/0
Extra: 0178ea13fc0cc883da95fba5ac403efcd6339fe8ea2e8383218a526c1eee1b4e31021100000001d3fcec30000000000000000000

1 output(s) for total of 21.787242019000 dcy

stealth address amount amount idx
00: a2e1e9e3f7d76f29044372924eef9f0d45d0e514d7fc47f847f7d60fa61c1065 21.787242019000 849219 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": 437564, "vin": [ { "gen": { "height": 437554 } } ], "vout": [ { "amount": 21787242019, "target": { "key": "a2e1e9e3f7d76f29044372924eef9f0d45d0e514d7fc47f847f7d60fa61c1065" } } ], "extra": [ 1, 120, 234, 19, 252, 12, 200, 131, 218, 149, 251, 165, 172, 64, 62, 252, 214, 51, 159, 232, 234, 46, 131, 131, 33, 138, 82, 108, 30, 238, 27, 78, 49, 2, 17, 0, 0, 0, 1, 211, 252, 236, 48, 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