Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03e6ea7f6d7d57822d2d79d720d1b10c50de1c7ebc1d5b2f7af620d61d0a15d7

Tx prefix hash: 6d3a208ce5ac8f0b26162cee567e9377f786dbe9127ad7df7f1c049ad293918a
Tx public key: 6efe363f6bb5a52c44cff01b78660eb39c8aa248bf75f23e8c14a59d7ac0f6e0
Timestamp: 1725097130 Timestamp [UCT]: 2024-08-31 09:38:50 Age [y:d:h:m:s]: 00:241:00:00:37
Block: 1099814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172120 RingCT/type: yes/0
Extra: 016efe363f6bb5a52c44cff01b78660eb39c8aa248bf75f23e8c14a59d7ac0f6e0021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2e7b6aa4beaee9b17aae9cc14de553bbd9786cbb72ea3374a0a87990c32e194 0.600000000000 1575783 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": 1099824, "vin": [ { "gen": { "height": 1099814 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2e7b6aa4beaee9b17aae9cc14de553bbd9786cbb72ea3374a0a87990c32e194" } } ], "extra": [ 1, 110, 254, 54, 63, 107, 181, 165, 44, 68, 207, 240, 27, 120, 102, 14, 179, 156, 138, 162, 72, 191, 117, 242, 62, 140, 20, 165, 157, 122, 192, 246, 224, 2, 17, 0, 0, 0, 5, 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