Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb5d8055c192d3ea05912b535ec4a6283e4dd5046ef0ba1c330cd3bf895c0c02

Tx prefix hash: 478a7927362424d5ff259381679257603aec80919dba2ac1f87b1a8260d1aaae
Tx public key: 09e4e4fcb77bb7e6a17c7b460852412d814fbfe68723129cd92c5a4ef47c4dc3
Timestamp: 1696641519 Timestamp [UCT]: 2023-10-07 01:18:39 Age [y:d:h:m:s]: 01:221:05:11:48
Block: 864105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419179 RingCT/type: yes/0
Extra: 0109e4e4fcb77bb7e6a17c7b460852412d814fbfe68723129cd92c5a4ef47c4dc3021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.841126787000 dcy

stealth address amount amount idx
00: ffd415e26ea6a434a9d3e78ce2181397da4fbd4aeeb6ca8bc8c5c8bf0d30a216 0.841126787000 1318613 of 0

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": 864115, "vin": [ { "gen": { "height": 864105 } } ], "vout": [ { "amount": 841126787, "target": { "key": "ffd415e26ea6a434a9d3e78ce2181397da4fbd4aeeb6ca8bc8c5c8bf0d30a216" } } ], "extra": [ 1, 9, 228, 228, 252, 183, 123, 183, 230, 161, 124, 123, 70, 8, 82, 65, 45, 129, 79, 191, 230, 135, 35, 18, 156, 217, 44, 90, 78, 244, 124, 77, 195, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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