Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99d135e48d7c542f0b69e00591ef5c1006685d328aa85244f9080c59a6ad9ea7

Tx prefix hash: cc08455be31387d4fe4891f3e306272b7757ff1bc638651afd612cbe99d837b3
Tx public key: 1bdb84f67e0d45f177f3ee6c35afdfa16fa4b83e50eb1a3615f6ce5f3a69e1a3
Timestamp: 1731829216 Timestamp [UCT]: 2024-11-17 07:40:16 Age [y:d:h:m:s]: 00:188:08:52:03
Block: 1155523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134501 RingCT/type: yes/0
Extra: 011bdb84f67e0d45f177f3ee6c35afdfa16fa4b83e50eb1a3615f6ce5f3a69e1a3021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a178c48db3a16c16dd0cb4f1d52b4319f2e9447e25f9ed5cf2b02e074d9c437 0.600000000000 1641140 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": 1155533, "vin": [ { "gen": { "height": 1155523 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a178c48db3a16c16dd0cb4f1d52b4319f2e9447e25f9ed5cf2b02e074d9c437" } } ], "extra": [ 1, 27, 219, 132, 246, 126, 13, 69, 241, 119, 243, 238, 108, 53, 175, 223, 161, 111, 164, 184, 62, 80, 235, 26, 54, 21, 246, 206, 95, 58, 105, 225, 163, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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