Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca63462829f7b21e1c3cdbe7875814d86dc2456b13d5bd369e9651f5d7cf6073

Tx prefix hash: 0f93c09258abe59aebf0cfbcf5b0c4db7205626bc010bff44f60ccea47895896
Tx public key: 8678f1eb9f39e7812cd194aadc99d2598d8c8699d6081b10c518b51470223aa1
Timestamp: 1580370701 Timestamp [UCT]: 2020-01-30 07:51:41 Age [y:d:h:m:s]: 04:293:16:06:38
Block: 54992 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1101033 RingCT/type: yes/0
Extra: 018678f1eb9f39e7812cd194aadc99d2598d8c8699d6081b10c518b51470223aa102110000012db221b3d1000000000000000000

1 output(s) for total of 403.449797112000 dcy

stealth address amount amount idx
00: 20a08fc3f2e96ebf8ff0794f87b0addafccf721fc7877780c2a0eb684fe730d6 403.449797112000 101663 of 0

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": 55002, "vin": [ { "gen": { "height": 54992 } } ], "vout": [ { "amount": 403449797112, "target": { "key": "20a08fc3f2e96ebf8ff0794f87b0addafccf721fc7877780c2a0eb684fe730d6" } } ], "extra": [ 1, 134, 120, 241, 235, 159, 57, 231, 129, 44, 209, 148, 170, 220, 153, 210, 89, 141, 140, 134, 153, 214, 8, 27, 16, 197, 24, 181, 20, 112, 34, 58, 161, 2, 17, 0, 0, 1, 45, 178, 33, 179, 209, 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