Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91283f4eebfb3563fcd76bce0adc38aa4b4b72e47c516a1728fb270c1e97ae93

Tx prefix hash: d8e4cf0184bddf7c440de4bd7660abcbb211e4ea05e10ff003f1f67073679a38
Tx public key: bfeb43c73bfd344c3a2c5267e5b9c4be11ead987f55508c1357b7093978fb1b9
Timestamp: 1749743868 Timestamp [UCT]: 2025-06-12 15:57:48 Age [y:d:h:m:s]: 00:150:08:28:47
Block: 1303539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105181 RingCT/type: yes/0
Extra: 01bfeb43c73bfd344c3a2c5267e5b9c4be11ead987f55508c1357b7093978fb1b90211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce68d9eee819a23f4493dbd9d46d5a06058f6f60aedabf82eacab50baf1ddf41 0.600000000000 1791122 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": 1303549, "vin": [ { "gen": { "height": 1303539 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce68d9eee819a23f4493dbd9d46d5a06058f6f60aedabf82eacab50baf1ddf41" } } ], "extra": [ 1, 191, 235, 67, 199, 59, 253, 52, 76, 58, 44, 82, 103, 229, 185, 196, 190, 17, 234, 217, 135, 245, 85, 8, 193, 53, 123, 112, 147, 151, 143, 177, 185, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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