Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46f2851ea4e9b2a60ee66927831471795d61175f951fbf52d2e3894bf7fa7580

Tx prefix hash: 760a1a504f797a4f1f63179c55ab47d18b3c31d9e9b158ba1e54ee168848a985
Tx public key: f8f29fb9e15b19a94a416ca00187ba7eb0d9ff1d37994154d4db8cff680dc6de
Timestamp: 1649626984 Timestamp [UCT]: 2022-04-10 21:43:04 Age [y:d:h:m:s]: 02:263:04:41:08
Block: 477533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 707894 RingCT/type: yes/0
Extra: 01f8f29fb9e15b19a94a416ca00187ba7eb0d9ff1d37994154d4db8cff680dc6de021100000001a8c141c5000000000000000000

1 output(s) for total of 16.059616716000 dcy

stealth address amount amount idx
00: e26b59458e60fb408ee868131f22776a34dbec232b69dd00fe90a9293ecec19a 16.059616716000 898204 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": 477543, "vin": [ { "gen": { "height": 477533 } } ], "vout": [ { "amount": 16059616716, "target": { "key": "e26b59458e60fb408ee868131f22776a34dbec232b69dd00fe90a9293ecec19a" } } ], "extra": [ 1, 248, 242, 159, 185, 225, 91, 25, 169, 74, 65, 108, 160, 1, 135, 186, 126, 176, 217, 255, 29, 55, 153, 65, 84, 212, 219, 140, 255, 104, 13, 198, 222, 2, 17, 0, 0, 0, 1, 168, 193, 65, 197, 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