Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 668dfb95bd19854f3428c2a6b02acd5f89129f347c5c81e2db09c91c5573365f

Tx prefix hash: 9fb0711e907bd4be4dea3368a4e4ef0ce3ac44c6120a39f5ec820ca47700bfdd
Tx public key: e0d53b61dc118734cfa5ae3fe3f28ae597418130d4dc377b0792efc9216e9cda
Timestamp: 1715434397 Timestamp [UCT]: 2024-05-11 13:33:17 Age [y:d:h:m:s]: 00:326:10:08:29
Block: 1019729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233287 RingCT/type: yes/0
Extra: 01e0d53b61dc118734cfa5ae3fe3f28ae597418130d4dc377b0792efc9216e9cda021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 945851ffe09653613a933a82eefbb63acb369d7b089a1bacb524b81bda2915bf 0.600000000000 1483770 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": 1019739, "vin": [ { "gen": { "height": 1019729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "945851ffe09653613a933a82eefbb63acb369d7b089a1bacb524b81bda2915bf" } } ], "extra": [ 1, 224, 213, 59, 97, 220, 17, 135, 52, 207, 165, 174, 63, 227, 242, 138, 229, 151, 65, 129, 48, 212, 220, 55, 123, 7, 146, 239, 201, 33, 110, 156, 218, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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