Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5271d0094c67830bc677f56eeae7177aa2b4c0fff18d16d1aacf6e53cd004e25

Tx prefix hash: 8c9af58a8efdc5428cf618ad633ed1df39dc7c086197d237186666ccfcef4add
Tx public key: d3748103143e2d7d8ec69dc2bbbf2d4efd7cb1d182fb509d5f22921034030473
Timestamp: 1705577737 Timestamp [UCT]: 2024-01-18 11:35:37 Age [y:d:h:m:s]: 01:082:03:14:37
Block: 937970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319799 RingCT/type: yes/0
Extra: 01d3748103143e2d7d8ec69dc2bbbf2d4efd7cb1d182fb509d5f2292103403047302110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e38b724c464938f0a68ac8080f73fd520117cd40709dc41de6f515492bde0226 0.600000000000 1396034 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": 937980, "vin": [ { "gen": { "height": 937970 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e38b724c464938f0a68ac8080f73fd520117cd40709dc41de6f515492bde0226" } } ], "extra": [ 1, 211, 116, 129, 3, 20, 62, 45, 125, 142, 198, 157, 194, 187, 191, 45, 78, 253, 124, 177, 209, 130, 251, 80, 157, 95, 34, 146, 16, 52, 3, 4, 115, 2, 17, 0, 0, 0, 3, 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