Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdbb7bd67b0ed5279b1aafaeae8f2cd3690d12e367be3b76cd6313f87b8a3cd3

Tx prefix hash: 98d37e2f781d94cc2be57540aef1f92f9f797cc67936f7b015fa7112f82b8723
Tx public key: a3713f6f01a50c3647cbb33f2cf491f406d0ec7812726b2a91e42b1c81289cf5
Timestamp: 1706421947 Timestamp [UCT]: 2024-01-28 06:05:47 Age [y:d:h:m:s]: 01:028:05:31:18
Block: 944960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281232 RingCT/type: yes/0
Extra: 01a3713f6f01a50c3647cbb33f2cf491f406d0ec7812726b2a91e42b1c81289cf502110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b6e3c79cffc852e3a3fe4c508389fb14142ab80773e22edfb74ef294672bbc6 0.600000000000 1403262 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": 944970, "vin": [ { "gen": { "height": 944960 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b6e3c79cffc852e3a3fe4c508389fb14142ab80773e22edfb74ef294672bbc6" } } ], "extra": [ 1, 163, 113, 63, 111, 1, 165, 12, 54, 71, 203, 179, 63, 44, 244, 145, 244, 6, 208, 236, 120, 18, 114, 107, 42, 145, 228, 43, 28, 129, 40, 156, 245, 2, 17, 0, 0, 0, 2, 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