Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcbbcf5fd45495381af05638fd6e974cce6dd0c3fbd3fc82d536fbe3566aabb8

Tx prefix hash: 48825a0cbb8e628ec1ff8fe5e6ce5ec941d09fd4fef3715809dd5d6ce750e53d
Tx public key: 3f459798730e697da9865a4db47afc960d81c74e2b97e091b19edbe15090f932
Timestamp: 1697853365 Timestamp [UCT]: 2023-10-21 01:56:05 Age [y:d:h:m:s]: 01:207:15:00:03
Block: 874149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 409435 RingCT/type: yes/0
Extra: 013f459798730e697da9865a4db47afc960d81c74e2b97e091b19edbe15090f932021100000004faf35c9c000000000000000000

1 output(s) for total of 0.779079017000 dcy

stealth address amount amount idx
00: fed692a03d66b949c8b0d1863a89d70ea4e4109dc34c921394e38444d4f986d4 0.779079017000 1329349 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": 874159, "vin": [ { "gen": { "height": 874149 } } ], "vout": [ { "amount": 779079017, "target": { "key": "fed692a03d66b949c8b0d1863a89d70ea4e4109dc34c921394e38444d4f986d4" } } ], "extra": [ 1, 63, 69, 151, 152, 115, 14, 105, 125, 169, 134, 90, 77, 180, 122, 252, 150, 13, 129, 199, 78, 43, 151, 224, 145, 177, 158, 219, 225, 80, 144, 249, 50, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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