Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72552c8d4fe5fb8675756d05b484c5c08e3943c4dc05b0363392741f8730d040

Tx prefix hash: 0b8f92cf5805570045b10a8445b18f8f5a2684a99942bf1d184cc7696d598ee0
Tx public key: 5e0e080cb9ff162f39a0a5046bdae5164fba6b449ae682027f48f117b0197df1
Timestamp: 1723499256 Timestamp [UCT]: 2024-08-12 21:47:36 Age [y:d:h:m:s]: 00:294:03:16:44
Block: 1086565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210144 RingCT/type: yes/0
Extra: 015e0e080cb9ff162f39a0a5046bdae5164fba6b449ae682027f48f117b0197df102110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fc35bb18ae9b1e523b178a206c4813906706cc7c1c19de94b5b802631d45f31 0.600000000000 1561162 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": 1086575, "vin": [ { "gen": { "height": 1086565 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fc35bb18ae9b1e523b178a206c4813906706cc7c1c19de94b5b802631d45f31" } } ], "extra": [ 1, 94, 14, 8, 12, 185, 255, 22, 47, 57, 160, 165, 4, 107, 218, 229, 22, 79, 186, 107, 68, 154, 230, 130, 2, 127, 72, 241, 23, 176, 25, 125, 241, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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