Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 870e92174b143dbbbcecdd7a584ae33f19627fd7e5c178c68a785507852e3cf2

Tx prefix hash: c4c9e498b7ac9e458893ca47815fa2a74183691824a37eed9e44ecf2df7e9ea5
Tx public key: 73c8d03afaf2c78baed1a10579341778d4b3736668b7b3a99fcb5e63fa320980
Timestamp: 1730772440 Timestamp [UCT]: 2024-11-05 02:07:20 Age [y:d:h:m:s]: 01:013:07:10:19
Block: 1146772 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267942 RingCT/type: yes/0
Extra: 0173c8d03afaf2c78baed1a10579341778d4b3736668b7b3a99fcb5e63fa320980021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c4d6310b1dff6e859d72b5870c9763a644596fd6c6627d63215a2fb5956d851 0.600000000000 1631463 of 15

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": 1146782, "vin": [ { "gen": { "height": 1146772 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c4d6310b1dff6e859d72b5870c9763a644596fd6c6627d63215a2fb5956d851" } } ], "extra": [ 1, 115, 200, 208, 58, 250, 242, 199, 139, 174, 209, 161, 5, 121, 52, 23, 120, 212, 179, 115, 102, 104, 183, 179, 169, 159, 203, 94, 99, 250, 50, 9, 128, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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