Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2c3bc7367530834a242f6d8cd001ff3cfb1173c891ef05f0b71cfe3ba1b40ad

Tx prefix hash: b685d2c3bf5cc2530aad42326dfb2387e1db624e36b311f1a0ea7bef9f79c975
Tx public key: 0b5cba5fde5cc1d541e76e17b91272ebadb4602f229cc5ab64cc65b30e811167
Timestamp: 1687453862 Timestamp [UCT]: 2023-06-22 17:11:02 Age [y:d:h:m:s]: 01:207:13:27:34
Block: 787980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 409731 RingCT/type: yes/0
Extra: 010b5cba5fde5cc1d541e76e17b91272ebadb4602f229cc5ab64cc65b30e81116702110000000275e3f0e9000000000000000000

1 output(s) for total of 1.503471851000 dcy

stealth address amount amount idx
00: 3f2a9fac5fc0103a18e7b5dfe8dd6e9a744f6be5f2604cb33be14a3da4d47e7a 1.503471851000 1238069 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": 787990, "vin": [ { "gen": { "height": 787980 } } ], "vout": [ { "amount": 1503471851, "target": { "key": "3f2a9fac5fc0103a18e7b5dfe8dd6e9a744f6be5f2604cb33be14a3da4d47e7a" } } ], "extra": [ 1, 11, 92, 186, 95, 222, 92, 193, 213, 65, 231, 110, 23, 185, 18, 114, 235, 173, 180, 96, 47, 34, 156, 197, 171, 100, 204, 101, 179, 14, 129, 17, 103, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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