Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa59dd88646969d4c2b48bfe47c64f10a58f7dbc9c88db5d2c5549ad379bf6c5

Tx prefix hash: 4cfd82fa84c05040127644ea13f9064fb5a7a7f5a26c84dfee9bd170644972b1
Tx public key: 06e59c0bbdfae6961afc8f9243316e91a639134eb4d99bfd0eec2b41c3276eba
Timestamp: 1704373341 Timestamp [UCT]: 2024-01-04 13:02:21 Age [y:d:h:m:s]: 01:140:05:58:45
Block: 928013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361360 RingCT/type: yes/0
Extra: 0106e59c0bbdfae6961afc8f9243316e91a639134eb4d99bfd0eec2b41c3276eba021100000003e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72a3f457ea8141fa91360a4612c306b962cc4ab861963106ea1f29d3108d5fdf 0.600000000000 1385869 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": 928023, "vin": [ { "gen": { "height": 928013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72a3f457ea8141fa91360a4612c306b962cc4ab861963106ea1f29d3108d5fdf" } } ], "extra": [ 1, 6, 229, 156, 11, 189, 250, 230, 150, 26, 252, 143, 146, 67, 49, 110, 145, 166, 57, 19, 78, 180, 217, 155, 253, 14, 236, 43, 65, 195, 39, 110, 186, 2, 17, 0, 0, 0, 3, 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