Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e0c92d4bbdd0492d24f532bd4c748739e209dbefa45f14c2071c0f864e2872b

Tx prefix hash: 3a7bd838235dad6debc356871c328709eeeea79ced0aa8f1f019744aa53637b6
Tx public key: fbd7b8d6dc729b16a16cea23829dd20a18172f87ccd2572044147fe56f52aef6
Timestamp: 1583236565 Timestamp [UCT]: 2020-03-03 11:56:05 Age [y:d:h:m:s]: 05:220:17:15:39
Block: 75440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1310513 RingCT/type: yes/0
Extra: 01fbd7b8d6dc729b16a16cea23829dd20a18172f87ccd2572044147fe56f52aef60211000001940aca7173000000000000000000

1 output(s) for total of 345.172954579000 dcy

stealth address amount amount idx
00: ea3e0bb58bd090c721b1be9b3b4f1410c14d93df97e9ae91a8012661848f28e1 345.172954579000 139379 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": 75450, "vin": [ { "gen": { "height": 75440 } } ], "vout": [ { "amount": 345172954579, "target": { "key": "ea3e0bb58bd090c721b1be9b3b4f1410c14d93df97e9ae91a8012661848f28e1" } } ], "extra": [ 1, 251, 215, 184, 214, 220, 114, 155, 22, 161, 108, 234, 35, 130, 157, 210, 10, 24, 23, 47, 135, 204, 210, 87, 32, 68, 20, 127, 229, 111, 82, 174, 246, 2, 17, 0, 0, 1, 148, 10, 202, 113, 115, 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