Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc161bdf736001fbdfa353a4a9a3fbcaae614ff3a70a364c0f1a37058fe1ce8c

Tx prefix hash: 34f63943de85f2e25a6c703aca9942c74462dcbaf2941fda97d8bdc464f5077e
Tx public key: 9007fb9f2385875147682cdd8e6ef225308176c0af4e727b14c1012bbdfa6b8b
Timestamp: 1731861727 Timestamp [UCT]: 2024-11-17 16:42:07 Age [y:d:h:m:s]: 00:172:22:47:46
Block: 1155798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123447 RingCT/type: yes/0
Extra: 019007fb9f2385875147682cdd8e6ef225308176c0af4e727b14c1012bbdfa6b8b0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6ce1267c4161b441ac300435a4730c4c797935178a5b818e8b15730ff5d2f63 0.600000000000 1641417 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": 1155808, "vin": [ { "gen": { "height": 1155798 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6ce1267c4161b441ac300435a4730c4c797935178a5b818e8b15730ff5d2f63" } } ], "extra": [ 1, 144, 7, 251, 159, 35, 133, 135, 81, 71, 104, 44, 221, 142, 110, 242, 37, 48, 129, 118, 192, 175, 78, 114, 123, 20, 193, 1, 43, 189, 250, 107, 139, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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