Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ab87b699882acaf21a66ca7ca9fa81b1baefe35fe655a3334bfb31994b832dd

Tx prefix hash: 079796a7bd4ce5a7ba5dc5bfc4b80152a2647e00f621abfac669640713717b05
Tx public key: 4aa030b57608a4626e8ce6cf1c3a7e0136b2779c2c4d319a3de32f286a35522c
Timestamp: 1737461069 Timestamp [UCT]: 2025-01-21 12:04:29 Age [y:d:h:m:s]: 00:148:08:21:00
Block: 1202126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105758 RingCT/type: yes/0
Extra: 014aa030b57608a4626e8ce6cf1c3a7e0136b2779c2c4d319a3de32f286a35522c021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0299857541baf329b565a07fc506dbd76532832c92c2cd8abd86cfede401b8ae 0.600000000000 1688785 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": 1202136, "vin": [ { "gen": { "height": 1202126 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0299857541baf329b565a07fc506dbd76532832c92c2cd8abd86cfede401b8ae" } } ], "extra": [ 1, 74, 160, 48, 181, 118, 8, 164, 98, 110, 140, 230, 207, 28, 58, 126, 1, 54, 178, 119, 156, 44, 77, 49, 154, 61, 227, 47, 40, 106, 53, 82, 44, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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