Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3489a0de3b324ddb9029fb76197132fa93fdf4f403974a1e530002de0a07b78d

Tx prefix hash: d209d8d730f4289d7f967df6ddedc81dee7a1620eb2c905094a6431b7917d1b9
Tx public key: 285896853e49221a9fa9d5695286d08d4e55a4685e0ac8886b0499e8338a86e9
Timestamp: 1682844119 Timestamp [UCT]: 2023-04-30 08:41:59 Age [y:d:h:m:s]: 02:026:08:46:54
Block: 749767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 540998 RingCT/type: yes/0
Extra: 01285896853e49221a9fa9d5695286d08d4e55a4685e0ac8886b0499e8338a86e9021100000003e6d27f9c000000000000000000

1 output(s) for total of 2.012384156000 dcy

stealth address amount amount idx
00: 8db206a0b0d15fdeed8fbfdd8929db2dc1e182065b23ebb8929c129716e40422 2.012384156000 1197772 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": 749777, "vin": [ { "gen": { "height": 749767 } } ], "vout": [ { "amount": 2012384156, "target": { "key": "8db206a0b0d15fdeed8fbfdd8929db2dc1e182065b23ebb8929c129716e40422" } } ], "extra": [ 1, 40, 88, 150, 133, 62, 73, 34, 26, 159, 169, 213, 105, 82, 134, 208, 141, 78, 85, 164, 104, 94, 10, 200, 136, 107, 4, 153, 232, 51, 138, 134, 233, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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