Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ad13582dcab1ca06abf32f3a03a81e22a0dae223218c45cf264f2d07cb64bc7

Tx prefix hash: fce6510b411693af69fc04fe08cf3094af8aed3c57e1ae473e9a653963219d52
Tx public key: 9c310b9a7e3b46f8fbe845d45f4533e4684481c04e37c5bc1c69a2e28a9036e2
Timestamp: 1741082741 Timestamp [UCT]: 2025-03-04 10:05:41 Age [y:d:h:m:s]: 00:256:13:15:12
Block: 1231877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181109 RingCT/type: yes/0
Extra: 019c310b9a7e3b46f8fbe845d45f4533e4684481c04e37c5bc1c69a2e28a9036e20211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b4a4258d0247566ecfaab51c029c8d70216255157b8531a342ece8c9e8de73c 0.600000000000 1718788 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": 1231887, "vin": [ { "gen": { "height": 1231877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b4a4258d0247566ecfaab51c029c8d70216255157b8531a342ece8c9e8de73c" } } ], "extra": [ 1, 156, 49, 11, 154, 126, 59, 70, 248, 251, 232, 69, 212, 95, 69, 51, 228, 104, 68, 129, 192, 78, 55, 197, 188, 28, 105, 162, 226, 138, 144, 54, 226, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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