Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32587b765da2b602809acff7e1876ecd705632add1f4797fb5879d08b53b8a25

Tx prefix hash: 1ec4e01f5f716abdc6c67ce73fe7dc98e29f61e248f439d6890b2ad7ce4035f9
Tx public key: 21bff158f180435dddb3c13a2e9c187ab20f5f69a9678412fda780a8ba048a59
Timestamp: 1723738798 Timestamp [UCT]: 2024-08-15 16:19:58 Age [y:d:h:m:s]: 00:237:18:41:44
Block: 1088554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169817 RingCT/type: yes/0
Extra: 0121bff158f180435dddb3c13a2e9c187ab20f5f69a9678412fda780a8ba048a59021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 445d53b0bdfd3b04a690b85f1d3c2547a253a39bdfb1c7a75f680376c4d1b202 0.600000000000 1563171 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": 1088564, "vin": [ { "gen": { "height": 1088554 } } ], "vout": [ { "amount": 600000000, "target": { "key": "445d53b0bdfd3b04a690b85f1d3c2547a253a39bdfb1c7a75f680376c4d1b202" } } ], "extra": [ 1, 33, 191, 241, 88, 241, 128, 67, 93, 221, 179, 193, 58, 46, 156, 24, 122, 178, 15, 95, 105, 169, 103, 132, 18, 253, 167, 128, 168, 186, 4, 138, 89, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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