Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27f75a350a09260575cb36d9c3d5192757c20dab6aa16722fa1e8e0eee64db21

Tx prefix hash: 1b50d4356926b4847f1b33c79e7dd21ab95a505267ce04880711b54fe907f041
Tx public key: 231b9c50f3acd6e57c3d655d93134ad1fd41b8a3d4319b0d634a1210bf434c31
Timestamp: 1735870948 Timestamp [UCT]: 2025-01-03 02:22:28 Age [y:d:h:m:s]: 00:075:23:41:33
Block: 1189004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54105 RingCT/type: yes/0
Extra: 01231b9c50f3acd6e57c3d655d93134ad1fd41b8a3d4319b0d634a1210bf434c31021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd5f780fbe0bd5ea6cdd9caa811a3796ba680ee371b5472ba486e27599326852 0.600000000000 1675509 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": 1189014, "vin": [ { "gen": { "height": 1189004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd5f780fbe0bd5ea6cdd9caa811a3796ba680ee371b5472ba486e27599326852" } } ], "extra": [ 1, 35, 27, 156, 80, 243, 172, 214, 229, 124, 61, 101, 93, 147, 19, 74, 209, 253, 65, 184, 163, 212, 49, 155, 13, 99, 74, 18, 16, 191, 67, 76, 49, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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