Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb31010ea84fbd08965a4ca0b43ce89e95c1c5328139b4f6d0fcd7d965c94340

Tx prefix hash: 735bcac72e825e263017e369a235eaea57a306c2247e0fd542fd63fd7d7f6963
Tx public key: dd8219e4f5ce42cdfbf29d7dc9b2b8aff075ec2cb5c02b80a2d0cb6299b220e0
Timestamp: 1696204337 Timestamp [UCT]: 2023-10-01 23:52:17 Age [y:d:h:m:s]: 01:148:10:18:53
Block: 860480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367098 RingCT/type: yes/0
Extra: 01dd8219e4f5ce42cdfbf29d7dc9b2b8aff075ec2cb5c02b80a2d0cb6299b220e002110000000175e3f0e9000000000000000000

1 output(s) for total of 0.864714216000 dcy

stealth address amount amount idx
00: 5cd4ad00760c95600ba60c27eb859e7867a7d8c11c3c89f7e326aa517341346d 0.864714216000 1314768 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": 860490, "vin": [ { "gen": { "height": 860480 } } ], "vout": [ { "amount": 864714216, "target": { "key": "5cd4ad00760c95600ba60c27eb859e7867a7d8c11c3c89f7e326aa517341346d" } } ], "extra": [ 1, 221, 130, 25, 228, 245, 206, 66, 205, 251, 242, 157, 125, 201, 178, 184, 175, 240, 117, 236, 44, 181, 192, 43, 128, 162, 208, 203, 98, 153, 178, 32, 224, 2, 17, 0, 0, 0, 1, 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