Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c038a2024921b7526f2526e690aee2507ac4cfbe8264f0428b1e11bc403e2914

Tx prefix hash: fbbca0730243c1142f59e21679fde8c91c2ec94f7a94b8e6882bc3fc3b3fdc35
Tx public key: 34bb95dde9a1351bc40ced731c09399086af852d1bc1d088be0da4b33d708fb5
Timestamp: 1694068691 Timestamp [UCT]: 2023-09-07 06:38:11 Age [y:d:h:m:s]: 01:242:00:09:39
Block: 842759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 434080 RingCT/type: yes/0
Extra: 0134bb95dde9a1351bc40ced731c09399086af852d1bc1d088be0da4b33d708fb50211000000054b8f5122000000000000000000

1 output(s) for total of 0.989896194000 dcy

stealth address amount amount idx
00: bb931eeac3449bbf941e3806daed068d903cd265d9b04e8f2e7201f2b315b160 0.989896194000 1295911 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": 842769, "vin": [ { "gen": { "height": 842759 } } ], "vout": [ { "amount": 989896194, "target": { "key": "bb931eeac3449bbf941e3806daed068d903cd265d9b04e8f2e7201f2b315b160" } } ], "extra": [ 1, 52, 187, 149, 221, 233, 161, 53, 27, 196, 12, 237, 115, 28, 9, 57, 144, 134, 175, 133, 45, 27, 193, 208, 136, 190, 13, 164, 179, 61, 112, 143, 181, 2, 17, 0, 0, 0, 5, 75, 143, 81, 34, 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