Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 761f19e890b808b478624d94cfb891bfdec909edd44aaded876fa9c67a52604a

Tx prefix hash: a7b0c6eafbe44f5f7902884914c7d8c716357f999cb4d191de9824911a5a0c50
Tx public key: 5da5288c8fc8db3ebec801be27cfe5569a5fd8270d831b0aa6c925aa50be36fd
Timestamp: 1634730000 Timestamp [UCT]: 2021-10-20 11:40:00 Age [y:d:h:m:s]: 03:145:05:31:08
Block: 356777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 881767 RingCT/type: yes/0
Extra: 015da5288c8fc8db3ebec801be27cfe5569a5fd8270d831b0aa6c925aa50be36fd02110000000cf29d7abf000000000000000000

1 output(s) for total of 40.350610273000 dcy

stealth address amount amount idx
00: febd1a6e3590b3faff4e9d85bdf3fa9ce220403256ca30a64fbfff6afc7e0073 40.350610273000 727795 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": 356787, "vin": [ { "gen": { "height": 356777 } } ], "vout": [ { "amount": 40350610273, "target": { "key": "febd1a6e3590b3faff4e9d85bdf3fa9ce220403256ca30a64fbfff6afc7e0073" } } ], "extra": [ 1, 93, 165, 40, 140, 143, 200, 219, 62, 190, 200, 1, 190, 39, 207, 229, 86, 154, 95, 216, 39, 13, 131, 27, 10, 166, 201, 37, 170, 80, 190, 54, 253, 2, 17, 0, 0, 0, 12, 242, 157, 122, 191, 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