Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5435d7eee33927d5a0ae25871366dd541074d18b741fdef38e9bca0644b90be

Tx prefix hash: 726a1d44a75b50f597efaa4b5280646f04300ca1daa82db09ff9a50e877fddbb
Tx public key: bbbf3b6429224a1f57d091ec9df85e49b4642f15068cddda03cbcf1d5418c693
Timestamp: 1723283394 Timestamp [UCT]: 2024-08-10 09:49:54 Age [y:d:h:m:s]: 00:158:08:40:53
Block: 1084784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113269 RingCT/type: yes/0
Extra: 01bbbf3b6429224a1f57d091ec9df85e49b4642f15068cddda03cbcf1d5418c693021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5020e7e2a1b5e15823a48722d6153cf6dbfabfb3c33e280cb31aa672ac1b1a8 0.600000000000 1559183 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": 1084794, "vin": [ { "gen": { "height": 1084784 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5020e7e2a1b5e15823a48722d6153cf6dbfabfb3c33e280cb31aa672ac1b1a8" } } ], "extra": [ 1, 187, 191, 59, 100, 41, 34, 74, 31, 87, 208, 145, 236, 157, 248, 94, 73, 180, 100, 47, 21, 6, 140, 221, 218, 3, 203, 207, 29, 84, 24, 198, 147, 2, 17, 0, 0, 0, 2, 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