Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41ecbc41aaeaf887a4dbefb139b98ffc508bd92f13ae041a1e9c97bacaf0ae7d

Tx prefix hash: aca2a948565fda3169a2fdd3415234dda38d6ee2d1e0370d2d5dfb2f8b609ae9
Tx public key: 9201a971afcec744c2bbf72c87cb14a74a67afe97b3f6b8ff13098db3aa44c08
Timestamp: 1679450054 Timestamp [UCT]: 2023-03-22 01:54:14 Age [y:d:h:m:s]: 01:342:06:03:35
Block: 722280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 505233 RingCT/type: yes/0
Extra: 019201a971afcec744c2bbf72c87cb14a74a67afe97b3f6b8ff13098db3aa44c0802110000000275e3f0e9000000000000000000

1 output(s) for total of 2.481912166000 dcy

stealth address amount amount idx
00: bdfb405de89d3e930c337c7634de6fe3f67ff88f647b33e261451f4f6e735b80 2.481912166000 1167195 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": 722290, "vin": [ { "gen": { "height": 722280 } } ], "vout": [ { "amount": 2481912166, "target": { "key": "bdfb405de89d3e930c337c7634de6fe3f67ff88f647b33e261451f4f6e735b80" } } ], "extra": [ 1, 146, 1, 169, 113, 175, 206, 199, 68, 194, 187, 247, 44, 135, 203, 20, 167, 74, 103, 175, 233, 123, 63, 107, 143, 241, 48, 152, 219, 58, 164, 76, 8, 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