Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2922f172cb84235022bfe4c0a095943b787fca11ceb6837c4d75e74ba8f4137d

Tx prefix hash: 367db1bdf81978f6080788402444f6ab827826d09e35eb4a20a219251d40726c
Tx public key: 00aa7a94f2fd333c5e7f45c5724ddc93f8c5dfda7ef5cc4e77794eea3b4ca47b
Timestamp: 1720827710 Timestamp [UCT]: 2024-07-12 23:41:50 Age [y:d:h:m:s]: 00:248:03:54:30
Block: 1064431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177277 RingCT/type: yes/0
Extra: 0100aa7a94f2fd333c5e7f45c5724ddc93f8c5dfda7ef5cc4e77794eea3b4ca47b02110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0aa9620834e6136a983c8897c075b00def363ec5aeb910d73d8df7f79c43a7c 0.600000000000 1534958 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": 1064441, "vin": [ { "gen": { "height": 1064431 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0aa9620834e6136a983c8897c075b00def363ec5aeb910d73d8df7f79c43a7c" } } ], "extra": [ 1, 0, 170, 122, 148, 242, 253, 51, 60, 94, 127, 69, 197, 114, 77, 220, 147, 248, 197, 223, 218, 126, 245, 204, 78, 119, 121, 78, 234, 59, 76, 164, 123, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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