Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0051919af3d4a41d895388fce29712b27a445a23f021a96dd7aedcd65c4441f0

Tx prefix hash: f35417ec4de74eaa835065cc3f5f75218190ad9834d1a98a48544b8bee0a7059
Tx public key: 179478798100e0b8e7f051b0e9fd001202e99c6f11046f374ea951c9234ed219
Timestamp: 1709939640 Timestamp [UCT]: 2024-03-08 23:14:00 Age [y:d:h:m:s]: 00:353:04:23:46
Block: 974160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252506 RingCT/type: yes/0
Extra: 01179478798100e0b8e7f051b0e9fd001202e99c6f11046f374ea951c9234ed2190211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d9c487e183c654c50eaf5df028a409e252bf8a1cd30bd684a5eb36265e769d8 0.600000000000 1434111 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": 974170, "vin": [ { "gen": { "height": 974160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d9c487e183c654c50eaf5df028a409e252bf8a1cd30bd684a5eb36265e769d8" } } ], "extra": [ 1, 23, 148, 120, 121, 129, 0, 224, 184, 231, 240, 81, 176, 233, 253, 0, 18, 2, 233, 156, 111, 17, 4, 111, 55, 78, 169, 81, 201, 35, 78, 210, 25, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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