Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88e54a338de59756b6a670e2ec0c47f79a3c1688cd444d466d90c3827a5da512

Tx prefix hash: 43324855b410823cb91c0f36361d54521d893e84560180550f098a33797fbca6
Tx public key: a9daabfcb179e81f0e042418712158595e5fc3bd9ba12e3d000a7606f25d2861
Timestamp: 1578464524 Timestamp [UCT]: 2020-01-08 06:22:04 Age [y:d:h:m:s]: 05:298:11:23:04
Block: 41007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1361085 RingCT/type: yes/0
Extra: 01a9daabfcb179e81f0e042418712158595e5fc3bd9ba12e3d000a7606f25d2861021100000003d81c26c0000000000000000000

1 output(s) for total of 448.885028552000 dcy

stealth address amount amount idx
00: e6c5d9e18cc61a5c244a729c277b7d5460a78a42f308a3759d91ec232402c85b 448.885028552000 72633 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": 41017, "vin": [ { "gen": { "height": 41007 } } ], "vout": [ { "amount": 448885028552, "target": { "key": "e6c5d9e18cc61a5c244a729c277b7d5460a78a42f308a3759d91ec232402c85b" } } ], "extra": [ 1, 169, 218, 171, 252, 177, 121, 232, 31, 14, 4, 36, 24, 113, 33, 88, 89, 94, 95, 195, 189, 155, 161, 46, 61, 0, 10, 118, 6, 242, 93, 40, 97, 2, 17, 0, 0, 0, 3, 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