Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffd1b814b16616e30f210164cba23349f22a5dd17d958b96e6939e9e797a80ba

Tx prefix hash: f3f236ccb5763fab267bce4b88dc39fbb2f2737245cd7886632a4331b8671625
Tx public key: 882a168390bb77db547db32d1c9ccbd44673e8b1901c5f959726d812e3597e3a
Timestamp: 1726204907 Timestamp [UCT]: 2024-09-13 05:21:47 Age [y:d:h:m:s]: 00:062:18:29:43
Block: 1108991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44881 RingCT/type: yes/0
Extra: 01882a168390bb77db547db32d1c9ccbd44673e8b1901c5f959726d812e3597e3a02110000000de914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 145b4de89b5386c1b7a812ddd87c6d5df8b854777c36032a5fd4d239829dfb74 0.600000000000 1587088 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": 1109001, "vin": [ { "gen": { "height": 1108991 } } ], "vout": [ { "amount": 600000000, "target": { "key": "145b4de89b5386c1b7a812ddd87c6d5df8b854777c36032a5fd4d239829dfb74" } } ], "extra": [ 1, 136, 42, 22, 131, 144, 187, 119, 219, 84, 125, 179, 45, 28, 156, 203, 212, 70, 115, 232, 177, 144, 28, 95, 149, 151, 38, 216, 18, 227, 89, 126, 58, 2, 17, 0, 0, 0, 13, 233, 20, 221, 21, 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