Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d03bde9f69cb5d8d615eab2bef6b3f3f37f23ef78ce94d112e93f5176175291

Tx prefix hash: 83c13b940765fd11b01ee82d219bf60afd2998ab2e315418b2973bfbaeb74447
Tx public key: adfc7bb86e890d30a88ced9b813d76bc240d56d7d9130728f9e359c0f8da448a
Timestamp: 1708195165 Timestamp [UCT]: 2024-02-17 18:39:25 Age [y:d:h:m:s]: 01:043:04:21:47
Block: 959686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291887 RingCT/type: yes/0
Extra: 01adfc7bb86e890d30a88ced9b813d76bc240d56d7d9130728f9e359c0f8da448a0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb3912eb4161f50b6b73c1db9cb473cde8f6fd7e2caa46ef22106795f98af8c5 0.600000000000 1419239 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": 959696, "vin": [ { "gen": { "height": 959686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb3912eb4161f50b6b73c1db9cb473cde8f6fd7e2caa46ef22106795f98af8c5" } } ], "extra": [ 1, 173, 252, 123, 184, 110, 137, 13, 48, 168, 140, 237, 155, 129, 61, 118, 188, 36, 13, 86, 215, 217, 19, 7, 40, 249, 227, 89, 192, 248, 218, 68, 138, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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