Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff97648aec7acdaf0d79016d38fcef0860149efe378e9bdeb9d567aace0ae405

Tx prefix hash: 0c3698bfea90d6536238f5f4d0795f073cacd4cb86d2c6614a51881eeb432384
Tx public key: f695dbcfcc4938b390c6a7ec40554ad4e813283de53ec2545ea1f4bc8f2d5242
Timestamp: 1617116197 Timestamp [UCT]: 2021-03-30 14:56:37 Age [y:d:h:m:s]: 03:269:02:37:37
Block: 229772 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 951846 RingCT/type: yes/0
Extra: 01f695dbcfcc4938b390c6a7ec40554ad4e813283de53ec2545ea1f4bc8f2d524202110000037590ec05ad000000000000000000

1 output(s) for total of 106.337871156000 dcy

stealth address amount amount idx
00: 78bd9187e7c4d07e4cf8d728791d6b21ad2cec04a9d19d4d1647909e45c2ac15 106.337871156000 476836 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": 229782, "vin": [ { "gen": { "height": 229772 } } ], "vout": [ { "amount": 106337871156, "target": { "key": "78bd9187e7c4d07e4cf8d728791d6b21ad2cec04a9d19d4d1647909e45c2ac15" } } ], "extra": [ 1, 246, 149, 219, 207, 204, 73, 56, 179, 144, 198, 167, 236, 64, 85, 74, 212, 232, 19, 40, 61, 229, 62, 194, 84, 94, 161, 244, 188, 143, 45, 82, 66, 2, 17, 0, 0, 3, 117, 144, 236, 5, 173, 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