Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87abb61bd673445ea23ee9d78727816552c3c895957ed7858bc9e2e670726aa8

Tx prefix hash: 0f6f91452dfc2d78a304fdde244c1327a8a1512e3517449fc694dfa1c40b353a
Tx public key: 4109b3ec304626935045dbc9b61f165743a5b6c80a3ef83a8204d970e8f01323
Timestamp: 1583081220 Timestamp [UCT]: 2020-03-01 16:47:00 Age [y:d:h:m:s]: 05:278:13:03:33
Block: 74647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1351418 RingCT/type: yes/0
Extra: 014109b3ec304626935045dbc9b61f165743a5b6c80a3ef83a8204d970e8f01323021100000001d81c26c0000000000000000000

1 output(s) for total of 347.267626976000 dcy

stealth address amount amount idx
00: 2db8d8d4384f314fc8fab263a771cec38f7923c9e752d8f224731a27bc099134 347.267626976000 138095 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": 74657, "vin": [ { "gen": { "height": 74647 } } ], "vout": [ { "amount": 347267626976, "target": { "key": "2db8d8d4384f314fc8fab263a771cec38f7923c9e752d8f224731a27bc099134" } } ], "extra": [ 1, 65, 9, 179, 236, 48, 70, 38, 147, 80, 69, 219, 201, 182, 31, 22, 87, 67, 165, 182, 200, 10, 62, 248, 58, 130, 4, 217, 112, 232, 240, 19, 35, 2, 17, 0, 0, 0, 1, 216, 28, 38, 192, 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