Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b74a83adc3eaead6c27107c197224e272d6438f56de393b80fd5028be42ded1d

Tx prefix hash: bf28e405d3a5d9c44d9b51af2d0a82d4efe625e5eb34a52306125806ca66df3d
Tx public key: ddd4c451b7da750b9191ba8d462452e71ec2716a3c4afa0839b7f68c119a1ea0
Timestamp: 1674994958 Timestamp [UCT]: 2023-01-29 12:22:38 Age [y:d:h:m:s]: 01:296:01:01:25
Block: 685320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 472522 RingCT/type: yes/0
Extra: 01ddd4c451b7da750b9191ba8d462452e71ec2716a3c4afa0839b7f68c119a1ea0021100000004835e4d22000000000000000000

1 output(s) for total of 3.290412035000 dcy

stealth address amount amount idx
00: 5cf3c8fe6c8d6302c649d22fdb873a681a6b907e8cb91f905d1cf4e20be9ed80 3.290412035000 1127627 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": 685330, "vin": [ { "gen": { "height": 685320 } } ], "vout": [ { "amount": 3290412035, "target": { "key": "5cf3c8fe6c8d6302c649d22fdb873a681a6b907e8cb91f905d1cf4e20be9ed80" } } ], "extra": [ 1, 221, 212, 196, 81, 183, 218, 117, 11, 145, 145, 186, 141, 70, 36, 82, 231, 30, 194, 113, 106, 60, 74, 250, 8, 57, 183, 246, 140, 17, 154, 30, 160, 2, 17, 0, 0, 0, 4, 131, 94, 77, 34, 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