Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf69f71990ec64eabf0d65242d4df09c4e334a1a744f996ee85497cdb2a88be6

Tx prefix hash: c5c328c15874ce017a6e27fd75a878108d13c5ad8ef29d177afff0371e3b4eb5
Tx public key: 429429e13c4bb5f57feab9240d087ee250ebaefb804ee0cb775013aff08ea3a0
Timestamp: 1744320269 Timestamp [UCT]: 2025-04-10 21:24:29 Age [y:d:h:m:s]: 00:216:15:01:02
Block: 1258679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152548 RingCT/type: yes/0
Extra: 01429429e13c4bb5f57feab9240d087ee250ebaefb804ee0cb775013aff08ea3a0021100000003a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b926aba440a1b8c52c4fb6d88ef23bebb3c9e1c2a0d4bc3548ddb27d1200410 0.600000000000 1745816 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": 1258689, "vin": [ { "gen": { "height": 1258679 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b926aba440a1b8c52c4fb6d88ef23bebb3c9e1c2a0d4bc3548ddb27d1200410" } } ], "extra": [ 1, 66, 148, 41, 225, 60, 75, 181, 245, 127, 234, 185, 36, 13, 8, 126, 226, 80, 235, 174, 251, 128, 78, 224, 203, 119, 80, 19, 175, 240, 142, 163, 160, 2, 17, 0, 0, 0, 3, 161, 29, 186, 152, 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