Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7235508386ff36d54e58b8d7a4f685002eba845662f9ebc15b50f75d03fb41d1

Tx prefix hash: aeca4ea764c266226776706a8c20f9a0b81925a711b1edf7dae0a44ed61219ce
Tx public key: 06c627db807c348688af65e5a60b7dfea7638f1ae96b1a5b842de7e68d83ebd4
Timestamp: 1695886500 Timestamp [UCT]: 2023-09-28 07:35:00 Age [y:d:h:m:s]: 01:202:01:21:09
Block: 857846 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405479 RingCT/type: yes/0
Extra: 0106c627db807c348688af65e5a60b7dfea7638f1ae96b1a5b842de7e68d83ebd4021100000008faf35c9c000000000000000000

1 output(s) for total of 0.882267209000 dcy

stealth address amount amount idx
00: 6039cecacce0a2e6f77cc51b0d1ab470245eaac7ed2ebc61d3e7f4f0b2296fd4 0.882267209000 1311992 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": 857856, "vin": [ { "gen": { "height": 857846 } } ], "vout": [ { "amount": 882267209, "target": { "key": "6039cecacce0a2e6f77cc51b0d1ab470245eaac7ed2ebc61d3e7f4f0b2296fd4" } } ], "extra": [ 1, 6, 198, 39, 219, 128, 124, 52, 134, 136, 175, 101, 229, 166, 11, 125, 254, 167, 99, 143, 26, 233, 107, 26, 91, 132, 45, 231, 230, 141, 131, 235, 212, 2, 17, 0, 0, 0, 8, 250, 243, 92, 156, 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