Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 592f02912463c1ae3189ac07c730816709f6900ef375dd85bb4772eced1eebb7

Tx prefix hash: db7a831ba214017fab05f8c46f1e4341ca1746233e4ba292fd91ae9837d797d0
Tx public key: b565ad4d1f24dbf01046f76b55f2117bd1f717f375b20eb7a9c526a34750b116
Timestamp: 1729168555 Timestamp [UCT]: 2024-10-17 12:35:55 Age [y:d:h:m:s]: 00:073:05:28:51
Block: 1133564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52320 RingCT/type: yes/0
Extra: 01b565ad4d1f24dbf01046f76b55f2117bd1f717f375b20eb7a9c526a34750b11602110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11ae10db839ead81cc1bb1f1522d6a6fb5ab1dcfdc3caf9a607ce81d69c670e8 0.600000000000 1616723 of 15

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": 1133574, "vin": [ { "gen": { "height": 1133564 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11ae10db839ead81cc1bb1f1522d6a6fb5ab1dcfdc3caf9a607ce81d69c670e8" } } ], "extra": [ 1, 181, 101, 173, 77, 31, 36, 219, 240, 16, 70, 247, 107, 85, 242, 17, 123, 209, 247, 23, 243, 117, 178, 14, 183, 169, 197, 38, 163, 71, 80, 177, 22, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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