Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de9fd9cf15c4a7d7c436e05e3fbac29c76b46e18c2c4fd9f64a0d6d98ce5aae3

Tx prefix hash: d7f9b5eb377d5c361e7b43d24cabc9dc317f7b13eaa93105bf56c0e1f3ffde2f
Tx public key: 8948d0c54ba1e04f44e782803d775667d5b985d100a884473abac619879b5820
Timestamp: 1711471841 Timestamp [UCT]: 2024-03-26 16:50:41 Age [y:d:h:m:s]: 01:012:13:48:24
Block: 986879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269920 RingCT/type: yes/0
Extra: 018948d0c54ba1e04f44e782803d775667d5b985d100a884473abac619879b582002110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03d4bc1d26f19abb9a4b6c12ebbf2f9044e0cdb4c6f38f6a38e401e4e307ea2a 0.600000000000 1447114 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": 986889, "vin": [ { "gen": { "height": 986879 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03d4bc1d26f19abb9a4b6c12ebbf2f9044e0cdb4c6f38f6a38e401e4e307ea2a" } } ], "extra": [ 1, 137, 72, 208, 197, 75, 161, 224, 79, 68, 231, 130, 128, 61, 119, 86, 103, 213, 185, 133, 209, 0, 168, 132, 71, 58, 186, 198, 25, 135, 155, 88, 32, 2, 17, 0, 0, 0, 10, 89, 218, 211, 245, 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