Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 044862e08d28d4dea61bf501a9f7df28a65ee664c7ccddc63225809c34509954

Tx prefix hash: bbb1585af466ab904b833e02fd8efcfd4c094a6f27682f7419e1ca5ee5fd9bb1
Tx public key: cbc7c3f44a6c1097f84271c00cd21dfd8a7330316caffc4af6f3917451f2c733
Timestamp: 1701346959 Timestamp [UCT]: 2023-11-30 12:22:39 Age [y:d:h:m:s]: 01:085:03:28:55
Block: 902898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321976 RingCT/type: yes/0
Extra: 01cbc7c3f44a6c1097f84271c00cd21dfd8a7330316caffc4af6f3917451f2c73302110000000275e3f0e9000000000000000000

1 output(s) for total of 0.625639405000 dcy

stealth address amount amount idx
00: 0e6dab8d12f73f848c1c18acd6c241dbf97f1bf60c4fd096ba556a45945041bb 0.625639405000 1359561 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": 902908, "vin": [ { "gen": { "height": 902898 } } ], "vout": [ { "amount": 625639405, "target": { "key": "0e6dab8d12f73f848c1c18acd6c241dbf97f1bf60c4fd096ba556a45945041bb" } } ], "extra": [ 1, 203, 199, 195, 244, 74, 108, 16, 151, 248, 66, 113, 192, 12, 210, 29, 253, 138, 115, 48, 49, 108, 175, 252, 74, 246, 243, 145, 116, 81, 242, 199, 51, 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