Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf858eacedc2b2e0de53120dcd195bd0785083aef8fd66093bbdf70a09dd82c5

Tx prefix hash: e0cbdfe1de46b561582f0f3dd8790785d66a21e5f1940d86fcc969cabf2d4185
Tx public key: 14ad4a904e671e18b324ea182b196131408a19cb8b0612ec68f53d25699479fa
Timestamp: 1701404950 Timestamp [UCT]: 2023-12-01 04:29:10 Age [y:d:h:m:s]: 00:364:00:00:37
Block: 903385 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260643 RingCT/type: yes/0
Extra: 0114ad4a904e671e18b324ea182b196131408a19cb8b0612ec68f53d25699479fa021100000002e08532b6000000000000000000

1 output(s) for total of 0.623319137000 dcy

stealth address amount amount idx
00: f9e0b35969fa0b23c7c805ebbc562680e5a7b2ce1de90420627b6fd9087cc9f2 0.623319137000 1360064 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": 903395, "vin": [ { "gen": { "height": 903385 } } ], "vout": [ { "amount": 623319137, "target": { "key": "f9e0b35969fa0b23c7c805ebbc562680e5a7b2ce1de90420627b6fd9087cc9f2" } } ], "extra": [ 1, 20, 173, 74, 144, 78, 103, 30, 24, 179, 36, 234, 24, 43, 25, 97, 49, 64, 138, 25, 203, 139, 6, 18, 236, 104, 245, 61, 37, 105, 148, 121, 250, 2, 17, 0, 0, 0, 2, 224, 133, 50, 182, 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