Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e047c89c0a8ec7dc99b773f5c83d6811be21fc0e05b7f17a0f8609b1c27c01df

Tx prefix hash: 648c4f472017274e30a606740c65b065c69758c586576e3367b4069e1eee42e3
Tx public key: 3c4dfe96201ed99e58de4cdb36f173b7090a8f04e632e16b384d62fe4bc642ab
Timestamp: 1705612920 Timestamp [UCT]: 2024-01-18 21:22:00 Age [y:d:h:m:s]: 01:136:04:13:47
Block: 938261 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358465 RingCT/type: yes/0
Extra: 013c4dfe96201ed99e58de4cdb36f173b7090a8f04e632e16b384d62fe4bc642ab02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cefb2853c25884cdb96c1a3069e123b49e5337391ff1ae9f1fd14ee25819a402 0.600000000000 1396331 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": 938271, "vin": [ { "gen": { "height": 938261 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cefb2853c25884cdb96c1a3069e123b49e5337391ff1ae9f1fd14ee25819a402" } } ], "extra": [ 1, 60, 77, 254, 150, 32, 30, 217, 158, 88, 222, 76, 219, 54, 241, 115, 183, 9, 10, 143, 4, 230, 50, 225, 107, 56, 77, 98, 254, 75, 198, 66, 171, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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