Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f03b9d2a8725f35bad1bf7b1510c78f43fe8395dd4fa4423b5d54cf19e06ee86

Tx prefix hash: 596a0ec0a0b5c856d82af08703e61aa477738012d4858c4df722f02d2be823aa
Tx public key: a708df43eeac5038c16e3956d960d1be504073af60a309e1729df1c5a8606a25
Timestamp: 1713359549 Timestamp [UCT]: 2024-04-17 13:12:29 Age [y:d:h:m:s]: 01:032:21:28:09
Block: 1002499 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284478 RingCT/type: yes/0
Extra: 01a708df43eeac5038c16e3956d960d1be504073af60a309e1729df1c5a8606a2502110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 707c21ee1d665f723e3ffedba8600714ad844f66b7cb6de1e16659306adde3d5 0.600000000000 1463015 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": 1002509, "vin": [ { "gen": { "height": 1002499 } } ], "vout": [ { "amount": 600000000, "target": { "key": "707c21ee1d665f723e3ffedba8600714ad844f66b7cb6de1e16659306adde3d5" } } ], "extra": [ 1, 167, 8, 223, 67, 238, 172, 80, 56, 193, 110, 57, 86, 217, 96, 209, 190, 80, 64, 115, 175, 96, 163, 9, 225, 114, 157, 241, 197, 168, 96, 106, 37, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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