Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3df3fa5bda54fc7608b2171256f277703507eb2b2390b93d68a1c7260d73dd26

Tx prefix hash: 68fc14e7b042ac5f00d30f25209aef599b6234528e03f1d8a848be0df0728ef8
Tx public key: 8128306bb8039b8ab4911a954422186b0be065de58203161e8ed017e1d982aee
Timestamp: 1646841911 Timestamp [UCT]: 2022-03-09 16:05:11 Age [y:d:h:m:s]: 02:306:10:40:10
Block: 454785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 738526 RingCT/type: yes/0
Extra: 018128306bb8039b8ab4911a954422186b0be065de58203161e8ed017e1d982aee0211000000054a0f5013000000000000000000

1 output(s) for total of 19.103316741000 dcy

stealth address amount amount idx
00: 0d78abe726eab61d1fcebf326875d02136d6efd0b4247b9136f3a16fb4d9e00d 19.103316741000 870504 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": 454795, "vin": [ { "gen": { "height": 454785 } } ], "vout": [ { "amount": 19103316741, "target": { "key": "0d78abe726eab61d1fcebf326875d02136d6efd0b4247b9136f3a16fb4d9e00d" } } ], "extra": [ 1, 129, 40, 48, 107, 184, 3, 155, 138, 180, 145, 26, 149, 68, 34, 24, 107, 11, 224, 101, 222, 88, 32, 49, 97, 232, 237, 1, 126, 29, 152, 42, 238, 2, 17, 0, 0, 0, 5, 74, 15, 80, 19, 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