Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f230e22c6adca5eb71c9678739b5d7627658b5d7bd32dde3947479bc9f5c1e2

Tx prefix hash: 6be573dfd09a7c520ef2d8ce522e75b0f5f352d0afdbaa272a2a066c362df171
Tx public key: 9ad66ce7bd1304f8d4f54db656e214976868ea492ad00aa979c812bd389d7d71
Timestamp: 1701960562 Timestamp [UCT]: 2023-12-07 14:49:22 Age [y:d:h:m:s]: 01:130:12:22:20
Block: 908001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354438 RingCT/type: yes/0
Extra: 019ad66ce7bd1304f8d4f54db656e214976868ea492ad00aa979c812bd389d7d7102110000000633af99f4000000000000000000

1 output(s) for total of 0.601749488000 dcy

stealth address amount amount idx
00: ad396f1b9295381d2fd411e806b87573de896e8ce2b590a367b3358afe85da6c 0.601749488000 1365012 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": 908011, "vin": [ { "gen": { "height": 908001 } } ], "vout": [ { "amount": 601749488, "target": { "key": "ad396f1b9295381d2fd411e806b87573de896e8ce2b590a367b3358afe85da6c" } } ], "extra": [ 1, 154, 214, 108, 231, 189, 19, 4, 248, 212, 245, 77, 182, 86, 226, 20, 151, 104, 104, 234, 73, 42, 208, 10, 169, 121, 200, 18, 189, 56, 157, 125, 113, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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