Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b89eb7bf72964d033554af33fa319801be495d0ae667fd09505601be693471f1

Tx prefix hash: a4ade9022c726bc50bd45e9290723a23a79872e89d258f3999b3f90caaf3f592
Tx public key: 719401ae9b97dddcc5eded836dbc434d2dd05b9a2fd7a78006f37d5ef845dee1
Timestamp: 1748262442 Timestamp [UCT]: 2025-05-26 12:27:22 Age [y:d:h:m:s]: 00:175:10:35:46
Block: 1291330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123074 RingCT/type: yes/0
Extra: 01719401ae9b97dddcc5eded836dbc434d2dd05b9a2fd7a78006f37d5ef845dee10211000000021f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4d5704a2b802fed9d7a231337e2dcb2f6aee47efca8f5f45c78bc6081116720 0.600000000000 1778801 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": 1291340, "vin": [ { "gen": { "height": 1291330 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4d5704a2b802fed9d7a231337e2dcb2f6aee47efca8f5f45c78bc6081116720" } } ], "extra": [ 1, 113, 148, 1, 174, 155, 151, 221, 220, 197, 237, 237, 131, 109, 188, 67, 77, 45, 208, 91, 154, 47, 215, 167, 128, 6, 243, 125, 94, 248, 69, 222, 225, 2, 17, 0, 0, 0, 2, 31, 144, 81, 122, 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