Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75273f6fb7f189f0735666be3b43980a1b1b0921a3e37e57b56a3ca26d1a2cb1

Tx prefix hash: 8e5ed85cd6e78316646fefcb8067c429cdf474dbdfe20fb9f7663b3395b91831
Tx public key: 5c5a5b70cff60029d882ee12bdf5e9b8261f0c7170e92350a1f9e888ab9da0d9
Timestamp: 1716962482 Timestamp [UCT]: 2024-05-29 06:01:22 Age [y:d:h:m:s]: 00:314:16:58:30
Block: 1032378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224911 RingCT/type: yes/0
Extra: 015c5a5b70cff60029d882ee12bdf5e9b8261f0c7170e92350a1f9e888ab9da0d902110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89f1c91c234f41cedd2cf68fbc7fb30af7b70f24bf4d693f04588620b68c4710 0.600000000000 1500831 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": 1032388, "vin": [ { "gen": { "height": 1032378 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89f1c91c234f41cedd2cf68fbc7fb30af7b70f24bf4d693f04588620b68c4710" } } ], "extra": [ 1, 92, 90, 91, 112, 207, 246, 0, 41, 216, 130, 238, 18, 189, 245, 233, 184, 38, 31, 12, 113, 112, 233, 35, 80, 161, 249, 232, 136, 171, 157, 160, 217, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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