Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33f9e3699cdd71aa904038e03129fef21dcaf50fab88ea9722001a97fe984b88

Tx prefix hash: b4bfb8a44d7ba347a55a84d96cce86107f75d231e860cfdd671691bac54d8224
Tx public key: 55bd9ec1cee4af96f40e237e40d0d7b0ceb7423fdc7b36641ff32025d2a67adc
Timestamp: 1744147631 Timestamp [UCT]: 2025-04-08 21:27:11 Age [y:d:h:m:s]: 00:053:10:21:53
Block: 1257242 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38252 RingCT/type: yes/0
Extra: 0155bd9ec1cee4af96f40e237e40d0d7b0ceb7423fdc7b36641ff32025d2a67adc0211000000026c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7641d8e73338d570669257c2e223cf00df34cbf14d0dd780a6e05398040e4679 0.600000000000 1744361 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": 1257252, "vin": [ { "gen": { "height": 1257242 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7641d8e73338d570669257c2e223cf00df34cbf14d0dd780a6e05398040e4679" } } ], "extra": [ 1, 85, 189, 158, 193, 206, 228, 175, 150, 244, 14, 35, 126, 64, 208, 215, 176, 206, 183, 66, 63, 220, 123, 54, 100, 31, 243, 32, 37, 210, 166, 122, 220, 2, 17, 0, 0, 0, 2, 108, 152, 170, 61, 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